Add provenance scanner for diagnostics links - #293
Open
tomvothecoder wants to merge 25 commits into
Open
Conversation
tomvothecoder
marked this pull request as ready for review
August 14, 2026 00:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Closes #240.
Adds a diagnostics provenance scanner that discovers diagnostic archives, validates scanner inputs, and idempotently links case diagnostics through the API. Persists successful scanner provenance state so scans can be resumed safely, with deployment helpers and operational documentation for supported sites.
Also adds regression coverage for scanner-state lookup, authorization, validation, missing-machine handling, idempotent links, rollback behavior, and scanner ingestion behavior.
Validation
make backend-test(1003 passed; 100% coverage)Deployment Notes
Apply the included Alembic migration before enabling scheduled scanner jobs. Configure site credentials and scheduler entries as documented.